chore(deps): allow database ^6.0.0#18
Conversation
The previous `5.*|6.0.*` constraint capped utopia-php/database below 6.1.0, which is where the getDocument cache-lease (read-after-write fix) landed. That cap blocks the lease from reaching downstream consumers (cloud) that depend on both this package and server-ce. Loosen to ^6.0.0 so 6.1.0+ can resolve; the 6.x line is backward-compatible for usage's API. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Greptile SummaryThis PR widens the database dependency so newer 6.x releases can resolve. The main changes are:
Confidence Score: 3/5The dependency update is small, but the package compatibility range narrows for consumers that still resolve database 5.x. The changed files are limited to Composer metadata and the lockfile, and the intended 6.x uncap is straightforward. The remaining concern is install compatibility for existing consumers on the previously allowed 5.x line. composer.json
 T-Rex LogsWhat T-Rex did
Reviews (1): Last reviewed commit: "chore(deps): allow database ^6.0.0" | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| "psr/http-client": "^1.0", | ||
| "utopia-php/client": "^0.1|^0.2", | ||
| "utopia-php/database": "5.*|6.0.*", | ||
| "utopia-php/database": "^6.0.0", |
There was a problem hiding this comment.
The new constraint allows newer database 6.x releases, but it also removes all database 5.x releases that were accepted before. An application that still resolves utopia-php/database 5.x can no longer install this package after this change, even though this PR does not add code that requires a database 6-only API. If the goal is only to uncap the 6.x line, keep the existing 5.x range and widen the 6.x range.
| "utopia-php/database": "^6.0.0", | |
| "utopia-php/database": "5.*|^6.0.0", |
Why
utopia-php/usagepinnedutopia-php/databaseto5.*|6.0.*, which caps it below 6.1.0 — the release that added theDatabase::getDocument()cache lease (the cache-aside read-after-write fix). Because cloud depends on bothusageandserver-ce, this cap was the binding constraint preventing database 6.1.0+ from resolving downstream, so the lease never reached cloud.Change
Loosen the constraint to
^6.0.0(matches server-ce's^6.0.0). The lock now resolves database 6.2.0 + cache 3.1.0. The 6.x line is backward-compatible for the database APIusageconsumes — CI validates against the resolved versions.Part of the cache-lease propagation chain: cache 3.1.0 → database 6.1.0 → { server-ce ✅, usage (this PR) } → cloud.
🤖 Generated with Claude Code